se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Fall/Spring |
Prerequisites |
| ||||||||
Course Language | |||||||||
Course Type | Elective | ||||||||
Course Level | - | ||||||||
Mode of Delivery | - | ||||||||
Teaching Methods and Techniques of the Course | |||||||||
Course Coordinator | - | ||||||||
Course Lecturer(s) | - | ||||||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | |
Major Area Courses | X | |
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction to DBMS systems | |
2 | Data modelling with Entity Relationship Model. Data modelling with UML Use Case and Class Diagrams | Preparation of various scenarios to form a basis for the analysis work |
3 | Relational Model and Relational algebra | Examples of relations from realworld situations |
4 | Normalisation | Various examples to be normalised |
5 | Normalisation, Revised data model | |
6 | Structured Query Language(data definition) | SQL examples (with Oracle SQL) |
7 | Structured Query Language(constructing the database) | SQL examples from realworld situations |
8 | Structured Query Language(stored procedures and triggers) | Application based examples |
9 | Query optimisation | With Oracle facilities |
10 | Database processing, data integrity and security | “ “ “ |
11 | Database processing, concurrency and recovery | “ “ “ |
12 | Trends, web databases | Examples of web databases |
13 | Trends, data warehousing | |
14 | Review of the semester’s topics | |
15 | Presentation of the students’ projects | |
16 | Review of the Semester |
Course Notes/Textbooks | “Database Systems”, T Connoly, C. Begg, Addiison Wesley publishers |
Suggested Readings/Materials | “An Introduction to Database Systems”, C J Date, Addison Wesley“Database Management Systems”, R Ramakrishnan, J Gehrke, McGrawHill“Relational Database Principles”, C Ritchie, Letts Educational“Fundamentals of SQL programming”, R MataToledo, P K Cushman, Schaum’s Outlines“Oracle Programming: A Primer”, R Sunderraman, Addison Wesley |
Semester Activities | Number | Weigthing |
Participation | 15 | 5 |
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | 1 | 25 |
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 30 |
Final Exam | 1 | 40 |
Total |
Weighting of Semester Activities on the Final Grade | 60 | |
Weighting of End-of-Semester Activities on the Final Grade | 40 | |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | 15 | 4 | |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | 1 | ||
Presentation / Jury | |||
Project | 63 | ||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 5 | |
Final Exams | 1 | 10 | |
Total | 107 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest